Repository navigation
chore: version packages - #369
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 11, 2026 13:44
ed4b3cf to
fcd4a69
Compare
Bccorb
approved these changes
Nov 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
seamless-cli@0.30.1
Patch Changes
seamless initwarns when another program already holds a port the local stack publishes (5173, 3000, 5312, 5432, and 5174 with a separate console), andseamless checkfails on one. The stack publishes on 127.0.0.1 only, so a Vite dev server on[::1]:5173used to takehttp://localhost:5173in the browser while every check passed. Each warning says what the conflict breaks and how to find the program.checkalso asks the project's own compose file which services run, rather than matching container names across every running container.seamless initnames each local stack's Compose project after its directory plus a random suffix, and no longer pins container names. A second project scaffolded under a name used before (such as the quickstart'smy-app) used to share the first one's Compose project, sodocker compose upran the old project's built images, which crashed against the new starters (does not provide an export named 'requirePermission'), and reused its database. Two scaffolded projects can now also run side by side. Existing projects keep their compose file.seamless verifyrun without a seamless-auth-api checkout now says it is a contributor tool, where to clone the API, and thatseamless checkis the command for a scaffolded project. From an npx or global install it no longer prints a path inside the npm cache, andseamless verify --helpsays the same up front.